System and method for determination of network operation metrics and generation of network operation metrics visualizations

ABSTRACT

A distributed cloud computing system is disclosed that includes a controller configured to deploy a plurality of gateways in a first cloud computing network and logic, stored on non-transitory, computer-medium. The logic, upon execution by one or more processors, causes performance of operations including: generating a topology mapping of the first cloud computing network including a plurality of constructs and connections therebetween, wherein the plurality of constructs includes the plurality of gateways, receiving input corresponding to a selection of a source construct and a destination construct, determining a data transmission path between the source construct and the destination construct, generating a visualization illustrating the data transmission path, and causing rendering of the visualization on a display screen of a network device.

CROSS-REFERENCE FOR RELATED APPLICATIONS

This application claims the benefit of priority on U.S. Provisional Patent Application No. 63/013,529 filed Apr. 21, 2020, and U.S. Provisional Patent Application No. 63/020,425 filed May 5, 2020, the entire contents of both are incorporated by reference herein.

FIELD

Embodiments of the disclosure relate to the field of cloud networking. More specifically, one embodiment of the disclosure is directed to a system and method for providing operational visibility of an enterprise network spanning a single public cloud network or multiple public cloud networks.

GENERAL BACKGROUND

Until recently, businesses have relied on application software installed on one or more electronic devices residing in close proximity to its user (hereinafter, “on-premises electronic devices”). These on-premises electronic devices may correspond to an endpoint device (e.g., personal computer, cellular smartphone, netbook, etc.), a locally maintained mainframe, or even a local server for example. Depending on the size of the business, the purchase of the on-premises electronic devices and their corresponding software required a significant upfront capital outlay, along with significant ongoing operational costs to maintain the operability of these on-premises electronic devices. These operational costs may include the costs for deploying, managing, maintaining, upgrading, repairing and replacing these electronic devices.

Recently, more businesses and individuals have begun to rely on public cloud networks (hereinafter, “public cloud”) for providing users to a variety of services, from word processing application functionality to network management. A “public cloud” is a fully virtualized environment with a multi-tenant architecture that provides tenants (i.e., users) with an ability to share computing and storage resources while, at the same time, retaining data isolation within each user's cloud account. The virtualized environment includes on-demand, cloud computing platforms that are provided by a collection of physical data centers, where each data center includes numerous servers hosted by the cloud provider. Examples of different types of public cloud networks may include, but is not limited or restricted to AMAZON WEB SERVICES®, MICROSOFT® AZURE®, GOOGLE CLOUD PLATFORM™ or ORACLE CLOUD™ for example.

This growing reliance on public cloud networks is due, in large part, to a number of cost saving advantages offered by this particular deployment. However, for many types of services, such as network management for example, network administrators face a number of challenges when business operations rely on operability of a single public cloud or operability of multiple public cloud networks. For instance, where the network deployed by an enterprise relies on multiple public cloud networks (hereinafter, “multi-cloud network”), network administrators have been unable to effectively troubleshoot connectivity issues that occur within the multi-cloud network. One reason for such ineffective troubleshooting is there are no conventional solutions available to administrators or users to visualize connectivity of its multi-cloud network deployment. Another reason is that cloud network providers permit the user with access to only a limited number of constructs, thereby controlling the type and amount of network information accessible by the user. As a result, the type or amount of network information is rarely sufficient to enable an administrator or user to quickly and effectively troubleshoot and correct network connectivity issues.

Likewise, there are no conventional solutions to visually monitor the exchange of traffic between network devices in different public cloud networks (multi-cloud network) and retain state information associated with network devices with the multi-cloud network to more quickly detect operational abnormalities that may suggest a cyberattack is in process or the health of the multi-cloud network is compromised.

Further, conventional solutions fail to provide the ability to obtain and visual a data transmission path between constructs within a cloud network, and certainly when the constructs span across multiple cloud networks. For example, the PING command is a well-known command that sends data to a specific IP address on a network, and returns the time to transmit that data and to receive a response. However, the PING command fails to provide any information as to the path traveled and/or metric information corresponding to constructs comprising that the path.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the disclosure are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is a diagram of an exemplary embodiment of a distributed cloud management system including a controller managing constructs spanning multiple cloud networks according to some embodiments;

FIG. 2A is an exemplary illustration of a logical representation of a controller deployed within a cloud computing platform in accordance with some embodiments;

FIG. 2B is an exemplary illustration of a logical representation of the copilot logic deployed within a cloud computing platform according to some embodiments;

FIGS. 3A-3C are interface screens displaying portions of a dashboard of a visualization platform directed to illustrating information pertaining to network traffic and constructs within a cloud-computing environment according to some embodiments;

FIGS. 4A-4H are interface screens displaying portions of a topology mapping of a visualization platform directed to illustrating constructs and connections therebetween within a cloud-computing environment according to some embodiments; and

FIGS. 5A-5G are exemplary interface screens displaying portions of an aspect of a visualization platform directed to illustrating information describing the flow of network traffic through one or more constructs within a cloud-computing environment according to some embodiments;

FIG. 6 is a flowchart of an exemplary method of communications between the copilot logic, a controller and one or more gateways managed by the controller according to some embodiments;

FIGS. 7A-7B illustrate a flowchart of methods of tagging and searching performed by the copilot logic and illustrated in FIGS. 4A-5A according to some embodiments;

FIG. 8 is a flowchart of an exemplary method of the replay function performed by the copilot logic and illustrated in FIGS. 4G-4H according to some embodiments;

FIG. 9 is an exemplary illustration of a logical representation of logic deployed within a cloud computing platform according to some embodiments;

FIG. 10 is a flowchart of an exemplary method of comprising operations to determine a data transmission path within a cloud network and generate a visualization of the data transmission path according to some embodiments;

FIG. 11 is a flowchart of an exemplary method of comprising operations to determine a data transmission path within a cloud network and accompanying network metrics and generate a visualization of the data transmission path and network metrics according to some embodiments; and

FIGS. 12A-12D are exemplary interface screens displaying portions of additional aspects of a visualization platform directed to illustrating information describing the flow of network traffic through one or more constructs within a cloud-computing environment according to some embodiments.

DETAILED DESCRIPTION

Embodiments of the disclosure are directed to a system configured to provide operational visibility of a network that spans one or more cloud computing environments. According to one embodiment, the system may include a software instance that is operating in one or more cloud computing resources and is configured to collect information and render a graphic user interface (GUI) that provides an interactive, visual rendering of the connectively between constructs of a network spanning multiple (two or more) cloud computing environments (hereinafter, a “multi-cloud computing environment or a “multi-cloud network”). In other embodiments, the system includes the software instance and a controller configured to manage constructs deployed in one or more cloud computing environments such as within a multi-cloud environment and communicate with the software instance.

As will be discussed below in further detail, the software instance may query the controller for information using one or more Application Programming Interface (API) calls to retrieve information stored by the controller detailing status information of each construct managed by the controller. The controller obtains such information from one or more gateways deployed within a multi-cloud network, where the gateway(s) are configured to transmit this information to the controller on a periodic (or aperiodic) basis. It should be understood that, as discussed herein, the term “multi-cloud networks” refers a plurality of cloud networks, where each cloud network may constitute a public cloud network provided by a different cloud computing environment resource provider (hereinafter, “cloud provider”).

As is known in the art, a controller may be configured to program each gateway to control routing of network traffic such as by providing instructions to gateways as to how network traffic is routed among various gateways. As illustrative examples, the controller may instruct a gateway as to whether a virtual machine (VM) from one subnet work (hereinafter, “subnet”) may communicate directly with a VM from another subnet, or how network traffic will flow from a source to a destination within the cloud computing environment managed by the controller. In addition, embodiments of the disclosure discuss instructions provided by the software instance to the controller, which are then transmitted to one or more gateways by the controller and include instructions to transmit network data from the gateway to a routable address (e.g., an Internet Protocol “IP” address, etc.) of the software instance.

Therefore, as a general embodiment, the software instance may query the controller for data indicating a status and metadata of each construct managed by the controller and also receive network data from one or more gateways. The software instance includes logic that, upon execution by one or more processors (e.g., being part of the cloud computing resources), generates various visualizations that are a combination of the construct status and metadata (collectively “construct metadata”) and the network data. The construct metadata may include the status of each construct (e.g., active, inactive, etc.), the cloud in which each construct is located, a cloud provider associated with each construct, central processing unit (CPU) usage (when applicable), memory usage (when applicable), throughput rate (e.g., receive/transmit rate or “Rx/Tx rate”) (when applicable), path latencies, etc.

The visualizations may be interactive and provided to users such as network administrators, information technology (IT) professionals, or the like. Additionally, the visualizations may be configured to receive user input, which causes the logic of the software instance (“copilot logic”) to alter the visualizations. As discussed below and illustrated in the accompanying drawings, the visualizations may include, but are not limited or restricted to, a dashboard view providing overall status and health of the network as well as specific network parameters; a dynamic topology mapping that provides a visual rendering of each construct and links that identify communications between the constructs; and a network flow visualization providing various illustrations detailing how network traffic is flowing (or has flowed) through the cloud computing environment managed by the controller. Each of the visualizations may provide data spanning a multi-cloud network.

In some embodiments, responsive to the user input, the copilot logic may generate tags for one or more of the constructs via the topology mapping visualization and store those tags for searching. For example, further user input may be received causing the copilot logic to search the numerous constructs managed by the controller and display the tagged constructs, as well as any links therebetween, via the topology mapping. In yet some embodiments, responsive to received user input including one or more tags as search items, the copilot logic may generate visualizations illustrating the network flow of the corresponding tagged construct(s).

By querying the controller for construct metadata and receiving network data from one or more gateways, the copilot logic may generate the exemplary visualizations described above, and those shown in the accompanying drawings, that illustrate the flow of network traffic associated with one or more tagged constructs. As is noted throughout, the illustrated flow of network traffic may correspond to constructs deployed in multiple cloud networks. Such operability provides numerous advantages to users over conventional solutions by enabling users to tag one or more gateways residing in different public cloud networks with meaningful tags and search for construct parameters, construct status, link status and the flow of network traffic corresponding to that tag.

An additional functionality of the copilot logic is the generation of visualizations that illustrate changes to aspects of the network managed by the controller over time. For example, and as discussed below, the copilot logic may store the received data pertaining to the network (the network data and the construct metadata) for given points in time, e.g., t₁→t_(i) (where i>1). Upon receiving user input corresponding to a request to display the changes between two points in time, e.g., t₁ and t₂, the copilot logic compares the stored data for t₁ and t2, and generate a visual that highlights the change(s) between the network at t₁ and t₂. The term “highlight” may refer to any visual indicator or combination of visual indicators, such as color-coding constructs having changed parameters, varying the size of constructs having changed parameters, displaying a graphic (e.g., a ring) around constructs having changed parameters, displaying a window or other image that lists the detected changes in state of the network, which may spanning multiple public cloud networks, between time t₁ and time t₂, or other types of visual indicators.

Further embodiments of the disclosure are directed to determination of a data transmission path between a source construct and a destination construct in response to received user input. Some embodiments are also directed to generating metrics corresponding to the data transmission path. For example, embodiments of the disclosure are directed to receiving user input indicating a source construct and a destination construct, and determining the data transmission path therebetween. Embodiments further include generation of visualizations that illustrate the data transmission path either with respect to a plurality of additional constructs comprising a cloud computing environment or in an isolated view. Additionally, some embodiments are directed to generating metrics for one or more constructs included within the data transmission path, e.g., metrics corresponding to gateways forming “hops” within the data transmission path as well as of edges therebetween.

I. Terminology

In the following description, certain terminology is used to describe features of the invention. In certain situations, the term “logic” is representative of hardware, firmware, and/or software that is configured to perform one or more functions. As hardware, the logic may include circuitry having data processing or storage functionality. Examples of such circuitry may include, but are not limited or restricted to a microprocessor, one or more processor cores, a programmable gate array, a microcontroller, an application specific integrated circuit, wireless receiver, transmitter and/or transceiver circuitry, semiconductor memory, or combinatorial logic.

Alternatively, or in combination with the hardware circuitry described above, the logic may be software in the form of one or more software modules. The software module(s) may include an executable application, an application programming interface (API), a subroutine, a function, a procedure, an applet, a servlet, a routine, source code, a shared library/dynamic load library, or one or more instructions. The software module(s) may be stored in any type of a suitable non-transitory storage medium, or transitory storage medium (e.g., electrical, optical, acoustical or other form of propagated signals such as carrier waves, infrared signals, or digital signals). Examples of non-transitory storage medium may include, but are not limited or restricted to a programmable circuit; a semiconductor memory; non-persistent storage such as volatile memory (e.g., any type of random access memory “RAM”); persistent storage such as non-volatile memory (e.g., read-only memory “ROM”, power-backed RAM, flash memory, phase-change memory, etc.), a solid-state drive, hard disk drive, an optical disc drive, or a portable memory device. As firmware, the executable code may be stored in persistent storage.

The term “computerized” generally represents that any corresponding operations are conducted by hardware in combination with software and/or firmware.

The term “construct” may be construed as virtual or physical logic directed to a particular functionality such as a gateway, virtual private cloud network (VPC), sub-network, virtual machine instance, software application instance or the like. For instance, as an illustrative example, the construct may correspond to virtual logic in the form of software (e.g., a virtual machine), which may assign a device-specific address (e.g., a Media Access Control “MAC” address) and/or an IP address within an IP address range supported by to a particular IP subnet. Alternatively, in some embodiments, the construct may correspond to physical logic, such as an electronic device that is communicatively coupled to the network and assigned the MAC and/or IP address(es). Examples of electronic devices may include, but are not limited or restricted to a personal computer (e.g., desktop, laptop, tablet or netbook), a mobile phone, a standalone appliance, a sensor, a server, or an information routing device (e.g., a router, bridge router (“brouter”), etc.). It is contemplated that each construct may constitute at least logic residing as part of a public network, although certain constructs may be deployed as part of an “on-premises” (or local) network.

The term “gateway” may refer to a software instance deployed within a public cloud network or a virtual private cloud network deployed with the public cloud network and controls the flow of data traffic within and from the public cloud network (e.g., to one or more remote sites including computing devices that may process, store and/or continue the routing of data). Herein, each gateway may operate as a “transit gateway” or “spoke gateway,” which are gateways having similar architectures but are identified differently based on their location/configurations within a cloud computing environment. For instance, a “spoke” gateway is configured to interact with targeted instances while a “hub” gateway is configured to further assist in the propagation of data traffic (e.g., one or more messages) directed to a spoke gateway or a computing device within an on-premises network.

The term “controller” may refer to a software instance deployed within a cloud computing environment (e.g., resources of a public cloud network) that manages operability of certain aspects of one or more cloud computing environments spanning across different public cloud networks (multi-cloud network). For instance, a controller may be configured to collect information pertaining to each VPC and/or each gateway instance and configures one or more routing tables associated with one or more VPCs and/or gateway instances spanning a multi-cloud network to establish communication links (e.g., logical connections) between different sources and destinations. These sources and/or destinations may include, but are not restricted or limited to on-premises computing devices, gateway instances or other types of cloud resources.

The term “message” generally refers to information in a prescribed format and transmitted in accordance with a suitable delivery protocol. Hence, each message may be in the form of one or more packets, frames, or any other series of bits having the prescribed format.

The term “link” may be generally construed as a physical or logical communication path between two or more constructs. For instance, as a physical communication path, wired and/or wireless interconnects in the form of electrical wiring, optical fiber, cable, bus trace, or a wireless channel using infrared, radio frequency (RF), may be used. A logical communication path includes any communication scheme that enables information to be exchanged between multiple constructs

Finally, the terms “or” and “and/or” as used herein are to be interpreted as inclusive or meaning any one or any combination. As an example, “A, B or C” or “A, B and/or C” mean “any of the following: A; B; C; A and B; A and C; B and C; A, B and C.” An exception to this definition will occur only when a combination of elements, functions, steps or acts are in some way inherently mutually exclusive.

As this invention is susceptible to embodiments of many different forms, it is intended that the present disclosure is to be considered as an example of the principles of the invention and not intended to limit the invention to the specific embodiments shown and described

II. General Architecture—Copilot System

Referring to FIG. 1, a diagram of an exemplary embodiment of a distributed cloud management system 100 is shown, where the cloud management system 100 features a controller 102 for managing constructs residing in multiple cloud networks and a software instance 138 to visualize the managed constructs (hereinafter, “copilot logic”). More specifically, the controller 102 is configured to manage multiple constructs spanning multiple cloud networks, such as cloud (network) A 104 and cloud (network) B 106. In the exemplary illustration, cloud A 104 provides computing resources (“resources”) for a transit gateway 114 in communication with gateways 1181-1182 associated with virtual networks (VNETs) 116 ₁-116 ₂. Cloud B 106 provides resources for a transit gateway 120 in communication with gateways 124 ₁-124 ₂ associated with virtual private clouds (VPCs) 122 ₁-122 ₂. Cloud B 106 further provides resources for a native transit hub 126 in communication with VPCs 128 and 130. According to this embodiment of the disclosure, as shown in FIG. 1, the transit gateways 114, 120 and the native transit hub 126 are in communication with each other. Thus, as should be clearly understood that the controller 102 is managing several constructs, such as the illustrated gateways, that span multiple cloud networks.

Specifically, a first grouping of constructs 108 is deployed within the Cloud A 104, and second and third groupings of constructs 110, 112 are deployed within Cloud B 106. The controller 102 utilizes a set of APIs to provide instructions to and receive data (status information) associated with each of these constructs as well as status information pertaining to each connection between these constructs (link state). The construct metadata returned by a construct may depend on the type of construct (e.g., regions, VPCs, gateway, subnets, instances within the VPCs, etc.), where examples of construct metadata may include, but is not limited or restricted to one or more of the following construct parameters (properties): construct name, construct identifier, encryption enabled, properties of the VPC associated with that construct (e.g. VPC name, identifier and/or region, etc.), cloud properties in which the construct is deployed (e.g., cloud vendor in which the construct resides, cloud type, etc.), or the like. Clouds A and B as well as the controller 102 may deployed within the cloud computing resources 136; however, the illustration of FIG. 1 is configured such to provide sufficient detail of the constructs and connections with the Clouds A and B.

Additionally, the cloud management system 100 includes copilot logic 138 processing on cloud computing resources 136. In some embodiments, the copilot logic 138 may be logic hosted on a user's Infrastructure as a Service (IaaS) cloud or multi-cloud environment. As one example, the copilot logic 138 may be launched as an instance within the public cloud networks (e.g., as an EC2® instance in AWS®). As an alternative example, the copilot logic 138 may be launched as a virtual machine in AZURE®. When launched, the copilot logic 138 is assigned a routable address such as a static IP address for example.

As shown, the copilot logic 138 is in communication with the controller 102 via, for example, an API that enables the copilot logic 138 to transmit queries to the controller 102 via one or more API calls. The copilot logic 138, upon execution by the cloud computing resources 136, performs operations including querying the controller 102 via API calls for construct metadata in response to a particular event. The particular event may be in accordance with a periodic interval or an aperiodic interval or a triggering events such as a user request for a visualization via user input.

In some embodiments, in response to receiving a query via an API call from the copilot logic 138, the controller 102 accesses data stored on or by the controller 102 and returns the requested data via the API to the copilot logic 138. For example, the copilot logic 138 may initiate one or more queries to the controller 102 to obtain topology information associated with the constructs managed by the controller 102 (e.g., a list of all gateways managed by the controller 102, a list of all VPCs or VNETs managed by the controller 102, or other data gathered from database tables) along with status information associated with each construct as described above.

Upon receiving the requested construct metadata, the copilot logic 138 performs one or more analyses and determines whether any additional construct metadata needs to be requested. For example, the copilot logic 138 may provide a first query to the controller 102 requesting a list of all gateways managed by the controller 102. In response to receiving the requested construct metadata, the copilot logic 102 determines the interconnections between the gateways listed. Subsequently, the copilot logic 138 may provide a second query to the controller 102 requesting a list of all VPCs managed by the controller. In response to receiving the requested construct metadata, the copilot logic 138 determines the associations between each VPC and a corresponding gateway.

For example, in some embodiments, the received construct metadata provides detailed information for each gateway enabling the copilot logic 138 to generate a data object, e.g., a database table of the construct metadata, that represents a gateway. The data object representing the multiple gateways are cross-referenced to build out a topology mapping based on the parameters of each gateway, which may include, inter alia: cloud network user account name; cloud provider name; VPC name; gateway name; VPC region; sandbox IP address; gateway subnet identifier; gateway subnet CIDR; gateway zone; name of associated cloud computing account; VPC identifier; VPC state; parent VPC name; VPC CIDR; etc. Similarly, the construct metadata is also utilized to generate a data object representing each VPC object and each subnet object.

Additionally, in order to determine whether a connection within the network is between two transit gateways, a separate API call may be utilized by the copilot logic 138 to query the controller 102 for a listing of all transit gateways. Thus, the copilot logic 138 is then able to determine whether a connection between a first gateway and a second gateway is between two transit gateways. In some embodiments, as will be discussed below, the connections between transit gateways and the connections between a spoke gateway and a transit may be represented visually in two distinct methods.

In addition to receiving the construct metadata from the controller 102, the copilot logic 138 may also receive network data from one or more gateways managed by the controller 102. For example, the network data may include for each network packet, but is not limited or restricted to, an ingress interface, a source IP address, a destination IP address, an IP protocol, a source port for UDP or TCP, a destination port for UDP or TCP, a type and code for ICMP, an IP “Type of Service,” etc. In one embodiment, the network data may be transmitted to the copilot logic 138 from a gateway using an IP protocol, for example, UDP. In some embodiments, the network data is collected and exported via the NetFlow network protocol.

In order to configure a gateway to transmit the network data to the copilot logic 138, the copilot logic 138 may provide instructions to the controller 102, which in turn provides the instructions to each gateway managed by the controller 102. The instructions provide the IP address of the copilot logic 138, which is used as the IP address for addressing the transmission of the network data.

As will be discussed in detail below, the copilot logic 138 may generate a visualization platform comprising one or more interactive display screens. These display screens may include a dashboard, a topology mapping and a network flow visualization. Additionally, the visualization platform may be configured to receive user input that causes filtering of the of the displayed data.

For example, and still with reference to FIG. 1, the copilot logic 138 may generate a topology mapping visualization of the connections linking the constructs detected by the controller 102, which are illustrated by the constructs within a logical region 132 represented by Cloud A 104 and Cloud B 106. Additionally, the copilot logic 138 may generate various graphical user interfaces (GUIs) that illustrates network traffic flows, traffic flow heat maps, packet capture, network health, link latency, encryption, firewalls, etc., of network traffic flowing between, to and from constructs managed by the controller 102 as illustrated by a second logical region 134.

Embodiments of the disclosure offer numerous advantages over current systems that provide a dashboard illustrating parameters of a controller as current systems do not provide the ability to visualize connections between constructs deployed across multiple cloud networks, the state of resources and connections between resources for multiple clouds and the flow of network data through constructs spanning multiple clouds. As one example, an enterprise network may utilize resources deployed in a plurality of cloud networks and an administrator of the enterprise network may desire to obtain visualization of the status of all constructs and connections associated with these resources. However, because the enterprise network spans multiple cloud networks, conventional systems fail to provide such a solution. By merely obtaining a textual representation of a status of each construct within a single cloud (e.g., through a command line interface), an administrator is unable to obtain a full view of the constructs, connections therebetween and the status of each for the entire enterprise network. Further, detection of anomalous or malicious network traffic patterns may not be detectable in the manner provided by current systems.

As used herein, a visualization (or visual display) of the constructs, connections therebetween and the status of each is referred to as a topology mapping. Current systems fail to provide a topology mapping across multiple cloud networks and fail to allow an administrator to search across multiple cloud networks or visualize how changes in a state of a construct or connection in a first cloud network affects the state of a resource or connection in a second cloud network. In some embodiments, the topology mapping may automatically change as a state of a construct or connection changes or upon receipt of construct metadata updates in response to certain events such as at periodic time intervals (e.g., a “dynamic topology mapping”).

In some embodiments, a network may be deployed across multiple cloud networks using a plurality of controllers to manage operability of the network. In some such embodiments, each controller may gather the information from the network and constructs which it manages, and a single controller may obtain all such information, thereby enabling the visualization platform to provide visibility across a network (or networks) spanning multiple controllers.

Referring to FIG. 2A, an exemplary illustration of a logical representation of the controller 102 deployed within the cloud management system 100 is shown in accordance with some embodiments. The controller 102, as noted above, may be a software instance deployed within the cloud network to assist in managing operability of constructs within multiple public cloud networks. According to this embodiment, the controller 102 may be configured with certain logic modules, including, a VPC gateway creation logic 200, a communication interface logic 202 and a data retrieval logic 204. The controller 102 may also include a routing table database 206.

In some embodiments, the gateway creation logic 200 performs operations to create a gateway within a VPC including creating a virtual machine within a VPC, provide configuration data to the virtual machine, and prompt initialization of the gateway based on the configuration data. In one embodiment in which the cloud computing resources utilized are AWS®, the VPC gateway creation logic 200 launches a virtual machine within a VPC, the virtual machine being an AMAZON® EC2 instance. The virtual machine is launched using a pre-configured virtual machine image published by the controller 102. In the particular embodiment, the virtual machine image is an Amazon Machine Image (AMI). When launched, the virtual machine is capable of receiving and interpreting instructions from the controller 102.

The communication interface logic 202 may be configured to communicate with the copilot logic 138 via an API. The controller 102 may receive queries from the copilot logic 138 via one or more API calls and respond with requested data via the API.

The data retrieval logic 204 may be configured to access each construct managed by the controller 102 and obtain construct metadata therefrom. Alternatively, or in addition, the data retrieval logic 204 may receive such construct metadata that is transmitted (or “pushed”) from the constructs without the controller 102 initiating one or more queries (e.g., API calls).

The routing table database 206 may store VPC routing table data. For example, the controller 102 may configure a VPC routing table associated with each VPC to establish communication links (e.g., logical connections) between a transit gateway and cloud instances associated with a particular instance subnet. A VPC routing table is programmed to support communication links between different sources and destinations, such as an on-premise computing device, a cloud instance within a particular instance subnet or the like. Thus, the controller 102 obtains and stores information that reveals certain properties of resources (e.g., constructs such as gateways, subnets, VPCs, instances within VPCs, etc.) within the purview of the controller 102 as well as status information pertaining to the connections (communication links) between with these resources.

Referring to FIG. 2B, an exemplary illustration of a logical representation of the copilot logic 138 deployed within a cloud computing platform is shown in accordance with some embodiments. The copilot logic 138 may be a software instance deployed using the cloud computing resources 136 and is configured to communicate with the controller 102 and each of the gateways managed by the controller 102. The copilot logic 138 is configured with certain logic modules, including, a tagging logic 208, a tags database 210, an interface generation logic 212, a communication interface logic 214 and a topology snapshot logic 216. Additionally, the copilot logic 138 may include a snapshot database 218, a construct metadata database 220 and a network data database 222.

In some embodiments, the tagging logic 208, upon execution by one or more processors, performs operations as discussed below with respect to FIGS. 4A-5A and 7A-7B. In some embodiments, the tags generated by the tagging logic 208 may be stored in the tags database 210.

In some embodiments, the interface generation logic 212, upon execution by one or more processors, performs operations as discussed below and that cause generation of exemplary interactive user interfaces as illustrated in FIGS. 4A-5G. In some embodiments, the tags generated by the tagging logic 208.

In some embodiments, the communication interface logic 214, upon execution by one or more processors, performs operations as discussed herein pertaining to querying a controller for construct metadata, receiving the requested construct metadata and receiving the network data from one or more gateways managed by the controller. In some embodiments, the received construct metadata and network data may be stored in the construct metadata database 220 and the network data database 222 (which may be separate or a combined database).

In some embodiments, the topology snapshot logic 216, upon execution by one or more processors, performs operations as discussed below with respect to FIGS. 4G-4H and 8. In some embodiments, the snapshots (recorded data) generated by the topology snapshot logic 216 may be stored in the snapshot database 218.

III. Exemplary User Interfaces—Copilot System Visualization Platform

The exemplary user interfaces illustrated in FIGS. 3A-5G may be configured by the copilot logic 138 to be rendered and displayed on various display screens and via various applications. For example, each of the user interfaces illustrated in FIGS. 3A-5G may be configured to be displayed through a web browser on a computer display screen, a laptop, a mobile device, or any other network device that includes a web browser. Additionally, each of the user interfaces illustrated in FIGS. 3A-5G may be configured to be displayed through a dedicated software application installed and configured to be executed on any of the network devices described above. For example, the copilot logic 138 may be configured to provide the data and user interfaces described herein to a software application (known in the art as an “app”) that may be installed and configured to be executed by one or more processors of a network device. Thus, upon execution, the app causes the user interfaces described herein to be rendered on the display screen of the network device (or an associated display screen).

1. Dashboard

Referring now to FIGS. 3A-3C, graphical user interface (GUI) screens (or “interface screens”) displaying portions of a dashboard of a Copilot System visualization platform (“visualization platform”) with each portion configured to illustrate information obtained or determined by the Copilot System are shown according to some embodiments. The interface screens of FIGS. 3A-3C may collectively comprise a “dashboard” 300 that displays various attributes pertaining to a network that is deployed across one or more cloud providers, and notably across multiple cloud providers.

For example, the dashboard 300 as shown in FIG. 3A include several display portions 302, 306, and 308. The navigation panel 304 is also shown as part of the visualization platform generated by the copilot logic 138. The display portion 302 displays information pertaining to constructs managed by a controller, e.g., the controller 102 of FIG. 1, with the constructs deployed in one or more cloud networks. The information displayed may include, but is not limited or restricted to, the number of gateways deployed, the number of current virtual private network (VPN) users, the number of user accounts, the number of transient gateways (TGWs), the number of network connections (optionally filtered according to cloud computing service), etc.

The display portion 306 of FIG. 3A includes a listing of virtual data centers comprising resources of the network, again optionally spanning multiple cloud networks. Specifically, the display portion 306 includes user input fields (e.g., checkboxes) configured to receive user input indicating how whether displayed by the dashboard 300 is filtered by one or more particular cloud networks (e.g., AWS®, GOOGLE® CLOUD PLATFORM® (GCP), AZURE® ORACLE CLOUD INFRASTRUCTURE® (OCI)).

Further, display portion 308 illustrates a world map including a graphical representation, e.g., an icon, for each virtual data center listed in the display portion 306 and a position on the world map to signify its geographical location. The display portion 308 may be filtered in accordance with the selection of “Filter By Cloud” provided in the display portion 306 and may be configured to receive user input to adjust the magnification of the map (e.g., “zoom in” or “zoom out”).

The navigation panel 304 includes links to each of the general visualizations provided by the visualization platform including the dashboard 300, the topology mapping 400 (of FIGS. 4A-4E) and network flow visualization 500 (of FIGS. 5A-5G).

Referring now to FIG. 3B, an illustration of a portion of the dashboard 300 displaying a plurality of graphs and charts is shown through a plurality of display portions 310 and 312. Each of the display portions 310 and 312 each display a distribution of resources throughout a multiple cloud deployment.

For instance, as an illustrative embodiment, the display portion 310 features a number of bar graphs directed to resources managed by the controller; however, as should be understood by review of the drawings accompanying this disclosure, bar graphs are merely one type of illustration that may be utilized to present data and that the disclosure is not intended to be so limited to the specific graphical representation types shown. Display portion 310 illustrates that the data displayed on the dashboard corresponds to constructs and network traffic spanning multiple cloud networks by specifically displaying “Accounts by Cloud,” “Gateways by Cloud” and “Transit Gateways by Cloud.” Similarly, the display portion 312 provides graphical representations directed toward gateway metrics, including “Gateways by Type,” “Gateways by Region” and “Gateways by Size.”

Referring now to FIG. 3C, an illustration of another graphical representation of network functionality, based on data gathered and processed by the copilot logic 138 and displayed as part of the dashboard 300, is shown. More specifically, according to this illustrative embodiment, the display portion 314 provides a graphical representation of network traffic between resources spanning multiple cloud networks for an adjustable time period (e.g., 24 hours). The time period may be adjusted by the copilot logic 138 based on receipt of user input. For example, user input may be received corresponding to selection of a portion of the graph shown by the user. In response to such received user input, the copilot logic 138 may alter the graphical representation to target the selected portion that now may be represented by a smaller time interval, e.g., 15 minutes, 30 minutes, one hour, etc.

In some embodiments, the dashboard 300 (and other visualizations discussed in FIGS. 4A-5G) are generated are a result of user input requesting such visualizations. In some embodiments, in response to receiving the request, the copilot logic 138 will request the construct metadata as discussed above, and store the construct metadata and the latest network data received from the gateways in a data store (such as the construct metadata database 220 and/or the network data database 222, which as noted above, may be a single database). Additionally, the copilot logic 138 then generates the requested visualization based on the stored data.

In some embodiments, the copilot logic 138 will automatically update the visualizations (e.g., generate an updated visualization and cause the re-rendering of the display screen) at periodic time intervals (e.g., every 30 seconds, every 1 minute, etc.). In some embodiments, an updated visualization will be generated and displayed upon occurrence of a triggering event, such as receipt of user input requesting a refresh of the display screen. The updated visualizations will be updated based on newly received or obtained construct metadata and/or network data since the previous rendering.

2. Topology Mapping

Referring now to FIGS. 4A-4E, interface screens displaying portions of a topology mapping 400 of the visualization platform generated by the copilot logic 138 are shown according to some embodiments. Specifically, FIGS. 4A-4E illustrate a plurality of constructs that are deployed in one or more cloud networks managed by the controller 102 and connections between various constructs.

Referring to FIG. 4A, an exemplary illustration of a topology mapping 400 generated by the copilot logic 138 is shown in accordance with some embodiments. As shown, the topology mapping 400 includes a graphical representation of the constructs managed by a controller, e.g., the controller 102 of FIG. 1. The topology mapping 400 enables a user to visualize all known constructs, which may be deployed on a single cloud or across multiple cloud networks. In the exemplary illustration, it is seen that the constructs displayed are deployed on a plurality of cloud networks including AZURE®, GCP and AWS®.

The topology mapping 400 is an interactive display screen configured to receive various forms of user input (e.g., drag and reposition of constructs, select construct(s) to view construct parameters, input text, select settings, or activate buttons, etc.). The received user input may be configured reposition constructs, cause a display of construct parameters, apply filters, search for constructs, run diagnostics, apply tag(s), etc.

As illustrated in FIG. 4A, the construct 402, e.g., the gateway 402, is illustrated as being selected. In the embodiment shown, the selection of the gateway 402 results in the display of the parameters of the gateway 402 in the display portion 422. For instance, the display portion 422 may provide the name of the selected construct, “Gateway,” (gateway 402) user input buttons 424 and 426 configured to receive user input, and a listing 428 of construct parameters including whether the construct is encrypted, the cloud provider of the construct, the gateway name associated with the construct, the VPC identifier associated with the construct, the cloud type of the construct, the VPC region of the construct, whether the construct is a transit VPC, etc. It should be noted that the construct parameters may correspond to the construct metadata received by the controller 102 as discussed above and is not limited to the parameters illustrated in the drawings. Instead, the disclosure includes all parameters of the selected construct.

The topology mapping 400 also illustrates a plurality of connections between various constructs. With reference to the selected gateway 402, several connections (communication links) are illustrated, including but not limited to: link 412 to the gateway 404, link 414 to the transit gateway 406, a link 416 indirectly linking the gateway 402 to the transit gateway 410, etc. Additionally, the varying graphical indicia may indicate a difference in the link. For example, in some embodiments, a solid link may indicate a link between two spoke gateways or a gateway-to-transit gateway link. Additionally, in some embodiments, a dotted line may indicate a link between two transit gateways. Further, in some embodiments, the links may be color-coded to provide a visual indication as to the state of the link, e.g., green for active, and red for inactive.

The topology mapping 400 also illustrates constructs other than a gateway including subnets, such as the subnet 418, and virtual data centers, such as the virtual data center 420 (e.g., representing an AZURE® resource).

Referring to FIG. 4B, an exemplary illustration of a topology mapping 400 generated by the copilot logic 138 illustrating a diagnostic function is shown in accordance with some embodiments. As shown in FIG. 4A, the topology mapping 400 may display a button 426 (e.g., labeled “diagnostic”) configured to receive user input activating the button 26, which causes initiation of a diagnostic procedure to be performed by the copilot logic 138. Upon activation of the button 426, the copilot logic 138 causes rendering of the display box 430, which includes several input fields 432-438 each configured to receive user input that dictates aspects of the diagnostic procedure. As shown, the copilot logic 138 is configured to perform the diagnostic procedure on the selected construct (gateway 402); however, in other embodiments, the display box 430 may include an additional user input field configured to receive a construct on which the diagnostic procedure will be performed (or initiated from).

Additionally, the copilot logic 138 may be configured to provide a value indicating link latency located on or adjacent to one or more of the links illustrated in FIG. 4A. The copilot logic 138 may be configured to automatically send data packets (e.g., a ping) and determine the time the packet spent in transmission by analyzing the time the data packet was sent and the time the data packet was received (included in a response packet from the data packet's destination). The link latency for each link may be updated at periodic intervals, e.g., every 30 seconds, 60 second, etc., or in response to a triggering event (e.g., receipt of user input indicating a refresh of the visual). Although a subset of the links illustrated in FIG. 4A include an indication of link latency, such may be provided for all links. Advantageously, a visual of link latencies may be used by network administrators to reposition constructs (e.g., terminate and re-launch a virtual machine in a different subnet) in order to improve link latencies. Additionally, the visual of link latencies may be utilized to assess non-compliance with certain Quality of Service (QoS) levels (e.g., as set forth in a contract). Further, the copilot logic 138 may set latency thresholds and monitor link latencies such that a notification is generated or alteration of the topology mapping 400 when a link latency meets or exceeds a latency threshold (which may correspond to the certain QoS levels referenced above).

Referring to FIG. 4B, the input fields 432-434 are configured to receive user input of: a destination, and an interface, respectively. Buttons 436-438 are configured to be activated via user input corresponding to selection of a diagnostic procedure of either: a ping, or trace route, respectively. Although not shown, in other embodiments, input fields corresponding to selection of other diagnostic procedures may be provided, including a TCP dump and/or a link latency check, for example. As shown in FIG. 4B, in response to user input activating the button 436 (ping), the copilot logic 138 initiates a procedure in which a ping is transmitted from the selected construct (gateway 402) to the destination address provided in field 432 (e.g., IP address, 8.8.8.8). The result 440 of the ping are illustrated in real-time. Thus, via the diagnostic procedures provided by the copilot logic 138 through the topology mapping 400, a user may be provided with results of various diagnostic procedures performed on constructs spanning multiple cloud networks (e.g., a ping procedure may be performed between a first gateway deployed in a first cloud and a second gateway deployed in a second cloud) with a visual of the results provided via the visualization platform generated by the copilot logic 138.

Referring to FIG. 4C, an exemplary illustration of a topology mapping 400′ generated by the copilot logic 138 illustrating search and filter functions is shown in accordance with some embodiments. Another functionality provided by the copilot logic 138 a search within the topology mapping 400 and a filter of the displayed constructs based on the received user input, e.g., the search term. As shown, the display portion 422 may include an input field 442, e.g., a text box, configured to receive user input corresponding to a search term. In response to receiving user input at the input field 442, the copilot logic 138 performs a search of the constructs displayed in the topology mapping 400. The search may be of the stored construct metadata, wherein the search includes one or more queries to the construct metadata database 220 of FIG. 2B. The data returned from the one or more queries is then used to generate the topology mapping 400′, which is a filtered view of the topology mapping 400 being a display of only the constructs associated with the search term. For example, the search term may correspond to any of the construct parameters discussed above. The copilot logic 138 need not receive a specified parameter but may instead just search all construct parameters within the database 220 for a value corresponding to the search term.

It should be understood that the system of the disclosure may be filtered according to multiple search terms or parameters. Further, it will be understood that, as discussed throughout, the copilot logic 138 advantageously stores the construct metadata for constructs spanning multiple cloud networks. Thus, the filtered view provided as a result of the copilot logic 138 receiving one or more search terms may correspond to a plurality of constructs spanning multiple cloud networks.

Referring to FIG. 4D, an exemplary illustration of a topology mapping 400 generated by the copilot logic 138 illustrating a tagged construct is shown in accordance with some embodiments. As shown, the display portion 422 includes a user input button 424 (e.g., labeled “Add tag”), which corresponds to tagging function performed by the copilot logic 138. Responsive to receiving user input activating the button 424, a display box 444 is generated by the copilot logic 138 and configured to receive further user input corresponding to a tag (e.g., alphanumeric text) that is to be associated with one or more selected constructs. In the illustrative example of FIG. 4D, a single node, i.e., construct, is selected (gateway 402).

Upon activation of the “add” button via user input included within the display box 444, the tag “ccdata” will be generated and associated with the selected construct, the gateway 402. The generation and association of the tag with the selected includes several operations performed by the copilot logic 138. For example, the copilot logic 138 generates and stores a table, wherein the table may be stored in the tags database 210 of FIG. 2B. The table includes an association of the tag “ccdata” and a unique identifier of each of the selected constructs, a unique identifier of the gateway 402. Therefore, and discussed in more detail below, the tagging of a construct enables a user to search the topology mapping 400 for constructs by their associated tag or tags, which is advantageous to users as they no longer need to remember or search by unique identifiers, which are often long alphanumeric strings. Additionally, when a plurality of constructs are tagged with the same tag, a user may search for the tag, and the copilot logic 138 will in turn generate a display showing the plurality of constructs associated with the tag provided as a search term. In some embodiments, as shown in FIG. 4E, the topology mapping 400 may be filtered to display only the plurality of constructs associated with the tag provided as a search term. However, in other embodiments, although not shown, the entirety of constructs may be displayed while the plurality of constructs associated with the tag provided as a search term are displayed in a visually-different manner than those constructs not associated with the tag (e.g., highlighted, color-coded, etc.).

Referring to FIG. 4E, an exemplary illustration of a topology mapping 400″ generated by the copilot logic 138 illustrating the tagging function illustrated in FIG. 4D in conjunction with a search by tag function is shown in accordance with some embodiments. As was discussed above, the copilot logic 138 performs operations to generate a tag based on received user input and associate the tag with one or more selected constructs (e.g., the gateway 402 as discussed with respect to FIG. 4D). In the illustration shown in FIG. 4E, it is assumed that a similar set of operations as discussed in FIG. 4D have been performed and the constructs 450, including the gateway 402, have been tagged with the same tag, e.g., “ccdata.”

The topology mapping 400″ illustrates a view of the topology mapping 400 where the displayed constructs have been filtered by a search term, “ccdata,” as illustrated by the text 448 provided to the display box 422 as user input. Further, upon receiving the text 448 as user input, the copilot logic 138 illustrates the search term in the display box 422 (e.g., search term 446) and further filters the topology mapping 400 to display the topology mapping 400″, which illustrates the constructs associated with the search term 446.

As referenced above, the grouping of constructs 450 are assumed to have been tagged with “ccdata”; thus, upon receiving the search term 446 as user input, the copilot logic 138 queries the tags database 210 to retrieve the unique identifier of each construct tagged by with “ccdata.” Subsequently, the copilot logic 138 generates and causes display of the topology mapping 400″, which includes the grouping of constructs 450.

In addition, FIG. 4E illustrates a second aspect of the tagging functionality of the copilot logic 138, which is to perform operations to tag constructs in a single instance. As shown, the grouping of constructs 450 appear selected via user input. The copilot logic 138 is further configured to tag the selected constructs with the user input provided in the display box 452, the display of which is a result of the activation of the “add tag” button 424, as discussed above. Specifically, the display box 452 is shown to receive the user input 454 (Company 1). Therefore, in response to activation of the “add” button within the display box 452, the copilot will generate a tag of “Company 1” and associate each of the constructs within the grouping 450 to the tag of “Company 1.”

It should be noted that the illustrated example of FIG. 4E discloses yet another aspect of the tagging functionality of the copilot logic 138, which is that a construct may be associated with multiple tags. As shown, each construct of the grouping 450 is associated with at least two tags: “ccdata” and “Company 1.”

It should be understood that a tag is not merely replacing a construct identifier (such as an IP address) but as multiple resources may have the same tag or tags, tagging constructs allows a user to visualize where a specified subset of constructs is deployed throughout the entire network, which may span across multiple cloud networks. As is illustrated in and will be discussed with respect to FIGS. 5A-5G, a search by a tag or tags enables a user to visualize specific network data for constructs associated with the tag or tags.

Referring to FIG. 4F, an exemplary illustration of a topology mapping 400 generated by the copilot logic 138 illustrating an active user tracking function is shown in accordance with some embodiments. The view of the “topology” aspect of the topology mapping 400 of FIG. 4F includes the input buttons 454 and a display portion 456. The input button 454 (e.g., labeled “get active users”) may be configured to receive user input corresponding to a user request to visualize active users, e.g., associated with a selected gateway such as the gateway 452. An active user may be a user that is logged into a virtual private network (VPN) having access to resources provided be a cloud network. The display portion 456 may be configured to receive user input corresponding to a selection and initiation of a tracking function of a selected active user, e.g., the active user 458, and whether the tracking function is to track network traffic of the selected active user with the selected active user being the source or destination.

More specifically, as part of the construct metadata, the copilot logic 138 receives information pertaining to active users utilizing resources managed by the controller 102. Upon activation of the input button 454 via user input, the copilot logic 138 may query the construct metadata database 220 for active users pertaining to a selected gateway. Upon retrieving the active users of the selected gateway, the copilot logic 138 causes alteration of the topology mapping 400 by displaying a graphical representation of other indicia of the active users associated with the selected gateway. However, in some embodiments, a gateway need not be selected such that the copilot logic 138 retrieves active users for each gateway managed by the controller 102.

In the exemplary embodiment illustrated in FIG. 4F, it is assumed that the gateway 452 is selected and that the input button 454 has been activated via user input. a plurality of active users are shown logged into a VPN associated with the gateway 452 including the active user 458. Further, FIG. 4F illustrates that the display portion 456 has received user input corresponding to a selection of tracking network work such that network traffic having a destination address of the active user 458 will be tracked by the copilot logic 138. Tracking of the network traffic may include the monitoring the source IP address or the destination IP address of each data packet entering or exiting the selected gateway. In some embodiments, the tracked network traffic may be displayed using a graphical representation adjacent and/or connected to the graphical representation of the active user 458. As shown, the tracked network traffic having a destination IP address equal to the IP address of the active user 458 is illustrated via graphical representations 460 ₁-460 ₃ with each including the source IP address of the incoming data packet. In alternative embodiments, the tracked network traffic may be provided in a separate display portion adjacent to the topology mapping and/or in a log stored by the copilot logic 138.

Referring to FIGS. 4G-4H, exemplary illustrations of the topology mappings 400′″ and 400″″ generated by the copilot logic 138 illustrating a replay function are shown in accordance with some embodiments. The copilot logic 138 may configured with the functionality to save a state of each construct and connection managed by the controller 102 at a given time instance, either periodically or when user input is received to indicate such a save operation. The record of the state each construct and connections for a given time instance may collectively be referred to as a “snapshot.” The state of each construct may include a record of each parameter associated with the construct as discussed herein. Further, the copilot logic 138 may be configured to determine a difference, if applicable, of states for corresponding constructs and corresponding connections between a first snapshot and a second, subsequent snapshot. The copilot logic 138 may then generate an interface screen that illustrates the differences in state.

The illustration of FIG. 4G illustrates a snapshot of the topology mapping 400 at time instance t_(t) (the topology mapping 400′″) and the illustration of FIG. 411 illustrates an interface, the topology mapping 400″″, displaying a difference between a snapshot of the topology mapping 400 at time instances t_(t) and t₂. For example, the topology mapping 400″″ provides a visual distinction on constructs 466-470 indicating a change has taken place between the two time instances. Additionally, the display box 464 may be included that provides a listing of the differences by construct.

3. Network Flow Visualization

Referring now to FIGS. 5A-5G, interface screens displaying portions illustrating the flow of network traffic generated by the copilot logic 138 are shown according to some embodiments. Specifically, FIGS. 5A-5G illustrate visualizations representing the flow of network traffic (“network flow visualization 500”) among a plurality of constructs that are deployed in one or more cloud networks managed by the controller 102 and connections between various constructs.

As a brief recap, the dashboard 300 discussed above is configured to provided visualizations of the cloud computing environment parameters such as the number of active gateways, number of VPN users, details of the virtual data centers associated with the cloud computing environment managed by a controller, locations of the virtual data centers, etc. Additionally, the topology mapping 400 is configured to provide a visualization of how each construct managed by the controller is connected; thus, providing a visual of interactions of the entire cloud computing environment managed by the controller. Finally, the network flow visualization 500 is configured to provide visualizations of the network traffic flowing among constructs managed by the controller. Therefore, the visualization platform generated by the copilot logic 138 that includes the dashboard 300, the topology mapping 400 and the network flow visualization 500 provides a holistic view of the entire cloud computing environment managed by the controller, which as discussed throughout the disclosure, may span a plurality of cloud networks.

i. Overview

Referring now to FIG. 5A, an exemplary illustration of a visualization of the network flow visualization 500 generated by the copilot logic 138 is shown in accordance with some embodiments. As shown, the network flow visualization 500 includes a plurality of display portions 502-508 with the display portion 508 including a plurality of charts 510 ₁-510 _(i) (wherein i≤1). Generally, the network flow visualization 500 is directed to providing various filterable views of how network traffic is flowing (or has flowed) through the cloud computing environment managed by a controller, such as the controller 102 of FIG. 1.

The display portion 502 represents a header for the network flow visualization 500 configured to receive user input corresponding to a selection of a redirection to a particular aspect of the network flow visualization 500 such as: overview, trends, geolocation, flows and records, wherein each will be discussed further below. In particular, the display portion 502 indicates that the “overview” is the aspect of the network flow visualization 500 currently being displayed.

The display portion 504 provides several filtering options directed to time periods for which network traffic flow is to be displayed throughout the network flow visualization 500. For example, the display portion includes input field comprising date selectors configured to receive user input corresponding to a start time and an end time. Additionally, buttons may be provided that enable quick selections via a single click, that upon activation cause the copilot logic 138 to filter the displayed network traffic flow by a predetermined time period, such as but not limited or restricted to: “last hour,” “last day,” “last week,” “last month,” etc.

The display portion 506 is configured to provide additional filter options including filter by a specific category such as, but not limited or restricted to, source address, destination address, flow export (host), source port, destination portion, etc., and a corresponding search term (“filter item”). Further, the display portion 506 displays the active filters, when applicable. In the embodiment shown, the filter 446 (“ccdata”) previously discussed in FIG. 4E is currently being applied, which corresponds to a filtering of the data illustrated in the charts 510 ₁-510 _(i) of the display portion 508.

Importantly, as FIG. 5A illustrates, the tags generated via the topology mapping 400 may be utilized as search terms and applied as filters in the network flow visualization 500. Therefore, a user may provide user input via the topology mapping 400 causing the copilot logic 138 to generate a tag and associate the tag with one or more selected constructs that may be deployed in multiple cloud networks. Further, following the generation and association of the tag, e.g., “ccdata,” the copilot logic 138 may receive further user input via the network flow visualization 500 causing the copilot logic 138 to filter the displayed flow of the network traffic and display only the flow of network traffic among (e.g., between, to and from) the constructs tagged with “ccdata.”

In addition, as shown in FIGS. 5B-5C, the illustrations of the charts 510 ₁-510 _(i) of the display portion 508 may be filtered according to input received via the display portion 504, the category selection and search term input fields of display portion 506, and/or selection of data displayed in one or more of the charts 510 ₁-510 _(i).

Referring now to FIG. 5B, an exemplary illustration of a visualization of the network flow visualization 500 generated by the copilot logic 138 is shown in accordance with some embodiments. As shown, the network flow visualization 500 is filtered according to the filter 514, which corresponds to the selection of a portion of the chart 510 ₂ of FIG. 5A (e.g., the destination IP address 10.101.0.52). In response to receiving user input corresponding to the selection of the destination IP address 10.101.0.52, the copilot logic 138 filters the data displayed in each of the charts 510 ₁-510 _(i) to display network traffic information pertaining to the selection. As shown, the chart 510 ₂′ is displayed in an altered visual in comparison to the chart 510 ₂ of FIG. 5A. It should be understood that multiple filters may be applied simultaneously.

ii. Trends

Referring to FIG. 5C, an exemplary illustration of a visualization of the network flow visualization 500 generated by the copilot logic 138 directed to illustrating “trends” of the flow of the network traffic is shown in accordance with some embodiments. FIG. 5C illustrates the “trends” aspect of the network flow visualization 500, which includes the display portions 504-506 discussed with respect to FIGS. 5A-5B. Additionally, the “trends” aspect may include display portions 516-518, which include a graph over time of network traffic in bytes according to destination port name and a chart 518 ₁ illustrating a the network traffic in bytes of a plurality of destination port names. Although not shown, additional graphs and charts similar to those of display portion 516 may be also be displayed for data categories (e.g., those illustrated in FIG. 5B such as source IP, destination IP, destination ports and IPs, source ports and IPs, source port, etc.).

As shown, the network flow visualization 500 is filtered according to the filter 514, which was generated and applied via the “overview” aspect of the network flow visualization 500 and discussed above. Thus, the copilot logic 138 is configured to apply filters that are persistent throughout the network flow visualization 500, which means that a filter applied in one aspect, e.g., “overview,” will be maintained across other aspects, e.g., “trends” and filter the data illustrated therein.

Referring now to FIG. 5D, an exemplary illustration of a visualization of the network flow visualization 500 generated by the copilot logic 138 directed to illustrating a filtered view of the graph shown in FIG. 5C is shown in accordance with some embodiments. As illustrated in FIG. 5C, a portion of the graph of the display portion 516 was selected via the indicators 5D-5D. FIG. 5D illustrates that copilot logic 138 is configured to receive user input corresponding to selection of a portion of the graph, such as 5D-5D, and alter the magnification of the graph (e.g., zoom in) to highlight the selected portion. As the chart 518 ₁ of FIG. 5C corresponds to the graph of the display portion 516, the chart 518 ₁ is shown in FIG. 5D as the filtered version 518 ₁′ displaying network traffic data according to destination port name filtered by the selection 5D-5D.

iii. Geolocation

Referring to FIG. 5E, an exemplary illustration of a visualization of the network flow visualization 500 generated by the copilot logic 138 directed to illustrating “geolocation” of the flow of the network traffic is shown in accordance with some embodiments. FIG. 5E illustrates the “geolocation” aspect of the network flow visualization 500, which includes at least the display portion 506 discussed with respect to FIGS. 5A-5B (in some embodiments, the display portion 504 may be included as well). Additionally, the “geolocation” aspect may include display portions 520-522. The display portion 520 illustrates a “heat map,” which includes a map of a geographic region, e.g., a world map, that includes visual indicators as to a density of network traffic at various locations on the map. As shown in the illustrative embodiment of FIG. 5E, the heat map 520 includes visual indicators representing a heat map to illustrate the varying density of network traffic flowing among the constructs managed by the controller 102. Further, the charts 524 ₁-524 ₃ provide additional graphical representations of the network traffic data shown in the heat map 520 (e.g., network traffic in bytes per country and/or city, network traffic in bytes per destination port and source port, network traffic in bytes per destination IP and source IP). It should be understood that although three (3) charts are illustrated, an alternative number may be illustrated such as one (1), two (2) or more than three (3).

Specifically, the copilot logic 138 determines the density of the network traffic flowing among the constructs based on the construct metadata and the network data received from the controller 102 and the gateways managed by the controller 102, respectively. In some embodiments, the illustration of shown in FIG. 5E may be updated on a periodic or aperiodic basis (e.g., in response to a triggering event such as received user input initiating a refresh).

In a similar manner as was discussed above with respect to the user interfaces of FIGS. 3A-5D, the heat map 520 and the charts of the display portion 522 may be filtered in various manners such as through receipt of user input via the display portion 506, selection of a portion of any chart of the display portion 522, or via a persistent filter applied via a different “aspect” of the network flow visualization 500.

iv. Flows

Referring to FIG. 5F, an exemplary illustration of a visualization of the network flow visualization 500 generated by the copilot logic 138 directed to illustrating “flows” aspect of the network traffic is shown in accordance with some embodiments. FIG. 5F illustrates the “geolocation” aspect of the network flow visualization 500, which includes at least the display portion 506 discussed with respect to FIGS. 5A-5B (in some embodiments, the display portion 504 may be included as well). Additionally, the “flows” aspect may include display portions 526, 530 and 532. The display portion 526 illustrates a plurality of charts 528 ₁-528 ₂, which may be similar to charts of the display portion 522 but display content such as network traffic in bytes per source address and network traffic in bytes per destination address. It should be understood that although two (2) charts are illustrated, an alternative number may be illustrated such as one (1) or more than two (2).

The display portion 530 may be a visual of the number of source IPs and destination IPs managed by the controller 102. Additionally, the display portion 532 illustrates a graphical representation of network traffic flowing from source IPs to destination IPs. In some embodiments, such as that of FIG. 5F, the graphical representation may display a series of flow lines from a source IP address to a destination IP address, wherein each flow line is illustrated in a visually distinct manner (e.g., different colors for each flow line). The graphical representation may be configured to receive user input selecting a source or destination IP address, and responsive to receiving such user input, the copilot logic 138 is configured to alter the graphical representation to emphasis (or singularly display) the flow(s) associated with the selected IP address. Additionally, the content displayed in each of the display portions 524 and 520 may be filtered and adjusted in accordance with the selected IP address to provide network data corresponding to the selected IP address.

v. Records

Referring to FIG. 5G, an exemplary illustration of a visualization of the network flow visualization 500 generated by the copilot logic 138 directed to illustrating “records” aspect of the network traffic is shown in accordance with some embodiments. FIG. 5F illustrates the “records” aspect of the network flow visualization 500, which includes at least the display portions 504-506 discussed with respect to FIGS. 5A-5B.

Additionally, the “records” aspect of the network flow visualization 500 includes the display portion 534, which illustrates a graphical representation, for example, a table format, of details regarding the network traffic flows illustrated in FIG. 5F. For example, the table may include columns providing data pertaining to: a timestamp, a host, a destination IP address, a source IP address, the number of bytes in the flow at the time indicated by the timestamp, the direction of the flow of network traffic (ingress or egress), the number of data packets transmitted at the time indicated by the timestamp, etc.

IV. Logical Flow—Construct Metadata and Network Data Retrieval

Referring now to FIG. 6, a flowchart of an exemplary method of communications between the copilot logic, a controller and one or more gateways managed by the controller is shown according to some embodiments. Each block illustrated in FIG. 6 represents an operation performed in the method 600 of exchanging communications with a controller and receiving data from one or more gateways managed by the controller. Prior to the initiation of the method 600, it may be assumed that a distributed cloud management system, such as that illustrated in FIG. 1, has been deployed. The method 600 is initiated when a copilot logic, such as the copilot logic 138 of FIG. 1, queries a controller, such as the controller 102 of FIG. 1 for construct metadata (block 602). As discussed above, the queries may be via one or more API calls. Subsequently, the copilot logic 138 receives the requested construct metadata and stores the received data in a database, such as the construct metadata database 220 of FIG. 2B (block 604).

Further, the copilot logic receives network data from one or more gateways that are managed by the controller (block 606). The copilot logic proceeds to store the received network data in a database, such as the network data database 222 of FIG. 2B.

Following receipt of the construct metadata and the network data, the copilot logic generates one or more visualizations based on the received data (block 608). Exemplary visualizations that may be generated are illustrated in FIGS. 3A-5G; however, the visualizations that may be generated by the copilot logic are not limited to those illustrated.

Referring to FIGS. 7A-7B, a flowchart of methods of tagging and searching performed by the copilot logic and illustrated in FIGS. 4A-5A is shown according to some embodiments. Each block illustrated in FIGS. 7A-7B represents an operation performed in the method 700 of tagging and searching operations performed by the copilot logic. Prior to the initiation of the method 700, it may be assumed that a distributed cloud management system, such as that illustrated in FIG. 1, has been deployed. The method 700 is initiated when a copilot logic, such as the copilot logic 138 of FIG. 1, generates a topology mapping visualization and causes rendering via an interface user interface (block 702). Following generation of the topology mapping visualization, the copilot logic receives user input via the topology mapping visualization corresponding to selection of one or more constructions and further indicates a tag name (block 704). Responsive to the received user input, the copilot logic generates a table associating the unique identifier of the selected one or more constructs with the tag name (block 706).

Following the generation of the table, the method 700 may proceed to either block 708 and/or block 714. Referring to block 708, the copilot logic receives further user input indicating the tag name as a search term via the topology mapping visualization. Responsive to receiving the search term, the copilot logic queries a tag database storing the previously generated table to retrieve a unique identifier of each of the one or more tagged constructs associated with the search term (block 710). Following retrieval of the unique identifiers, the copilot logic performs operations causing alteration of the topology mapping visualization that visually distinguish the one or more tagged constructs associated with the search term from constructs not associated with the search term (block 712). For example, the alteration may include providing a visualization that only displays graphical representations of the tagged constructs associated with the search term and corresponding network data including links therebetween. However, other alternations have been considered such as increasing the size of the tagged constructs (and corresponding network data) associated with the search term relative to the other constructs and network data (or decreasing the size of the non-tagged constructs).

Referring now to FIG. 7B and block 714, following the generation of the table, the copilot logic generates a visualization of the flow of the network traffic among (between, to and/or from) one or more constructs managed by the controller. It should be noted that the operations of block 714 may be performed prior to the generation of the table in some embodiments. The copilot logic receives further user input via the visualization of the flow of the network traffic that indicates the tag name as a filter term (block 716).

Responsive to receiving the filter term, the copilot logic queries a tag database to retrieve the unique identifiers of each of the one or more constructs associated with the filter term (block 718). Following retrieval of the unique identifiers, the copilot logic performs operations causing alteration of the visualization of the flow of network traffic to display illustrations of only the flow of network traffic among the one or more constructs associated with the filter term (block 720). For example, an exemplary visualization is shown in FIG. 5A.

Referring now to FIG. 8, a flowchart of an exemplary method of the replay function performed by the copilot logic and illustrated in FIGS. 4G-4H is shown according to some embodiments. Each block illustrated in FIG. 8 represents an operation performed in the method 800 of operations performed by the copilot logic comprising a replay functionality. Prior to the initiation of the method 800, it may be assumed that a distributed cloud management system, such as that illustrated in FIG. 1, has been deployed. The method 800 is initiated when a copilot logic, such as the copilot logic 138 of FIG. 1, records, at a first-time instance, construct metadata and optionally at least a portion of network data for all constructs managed by a controller (block 802). Further, the copilot logic records, at a second, subsequent time instance, construct metadata and optionally at least a portion of network data for all constructs managed by the controller (block 804).

Following recording (e.g., storing in a database such as the snapshot database 218 of FIG. 2B) of the data at the first and second time instances and in response to user input indicating an initiation of a comparison between the state of the constructs managed by the controller (and links therebetween), the copilot logic performs a comparison between the recorded data at the first time instance with the recorded data at the second time instance (block 806).

In further response to the user input, the copilot logic generates a topology mapping visualization illustrating the one or more differences, if any, between the recorded data at the first- and second-time instances and causes a rendering via an interface user interface (block 808). Exemplary visualizations are shown in FIGS. 4G-4G; however, the visualizations that may be generated are not limited to those shown.

V. Network Operation Visualization and Metrics

Referring now to FIG. 9, an exemplary illustration of a logical representation of logic deployed within a cloud computing platform is shown according to some embodiments. As discussed above, the copilot logic 138 may be a software instance deployed using the cloud computing resources 900 ₁-900 _(n) (wherein n≥1), with the plurality of cloud computing resources 900 ₁-900 _(n) indicating that the possibility of a multi-cloud environment. The cloud computing resources 900 ₁-900 _(n) may also correspond to the cloud computing resources 136 in FIG. 1. The cloud computing resources 900 is shown to include at least server computing devices 902 and storage 904 (i.e., non-transitory, computer-readable medium).

The copilot logic 138 is configured to communicate with network devices such as the controller 102 and each of the gateways managed by the controller 102. The copilot logic 138 may be configured with certain logic modules, including, the tagging logic 208, the tags database 210, the interface generation logic 212, the communication interface logic 214 and the topology snapshot logic 216, as discussed above. Additionally, in some embodiments, the copilot logic 138 may further include a path determination logic 906 and a network metric determination logic 908. Additionally, the copilot logic 138 may include the snapshot database 218, the construct metadata database 220 and the network data database 222, discussed previously.

In some embodiments, the path determination logic 906, upon execution by one or more processors, performs operations including receiving user input corresponding to a selection of a source construct and a destination construct, and analyzing the construct metadata and the network data received associated with the source and destination constructs to determine a data transmission path between the source and destination constructs.

In one particular embodiment, the copilot logic 138 obtains the construct metadata and network data and, based on this, determines each construct within a cloud computing environment in which the controller is deployed and the connections between the constructs. As noted, the copilot logic 138 may obtain at least a portion of this data by calling APIs that facilitate communicate with the controller 102. The copilot logic 138 then builds a topology map based on the construct and connection data. The path determination logic 906 may then apply an algorithm on the topology map to determine a shortest path between two constructs. In one embodiment, the path determination logic 906 applies Dijkstra's algorithm on the topology map with inputs including a source construct and a destination construct. The path determination logic 906 may further verify the result of Dijkstra's algorithm by querying gateways included in the resultant shortest path to determine if the gateway includes the connections implicated in the resultant shortest path. When all connections implicated in the resultant shortest path are actual connections, the path determination logic 906 confirms the resultant shortest path is valid. However, when an implicated connection is not present, the resultant shortest path is deemed invalid.

In some embodiments, the network metric determination logic 908, upon execution by one or more processors, performs operations including computation of latency periods between gateways included in the data transmission path, a total latency period for the data transmission path, computation of CPU usage and memory usage by each of the gateways included in the data transmission path, and computation of throughput at each gateway included in the data transmission path.

Referring to FIG. 10, a flowchart of an exemplary method of comprising operations to determine a data transmission path within a cloud network and generate a visualization of the data transmission path is shown according to some embodiments. Each block illustrated in FIG. 10 represents an operation performed in the method 1000 of determining a data transmission path within a cloud network between a source construct and a destination construct and generating a visualization thereof. Prior to the initiation of the method 1000, it may be assumed that a distributed cloud management system, such as that illustrated in FIG. 1 and including the logic of FIG. 9, has been deployed. It is further assumed that the instance of the copilot logic 138 is in active communication with the controller 102 and each of the gateways managed by the controller such that the copilot logic 138 is regularly (e.g., periodically or aperiodically) receiving construct metadata and network data.

The method 1000 begins when the interface generation logic 212 in combination with the topology snapshot logic 216 generates one or more visualizations, such as a topology mapping visualization, based on the received construct metadata and network data (block 1002). Exemplary visualizations with respect to this operation are illustrated in FIGS. 3A-5G and 12A; however, the visualizations that may be generated by the copilot logic are not limited to those illustrated.

The path determination logic 906 of the copilot logic 138 may receive user input corresponding to a selection of a source construct and a destination construct (block 1004). In some embodiments, the user input may be received through the topology mapping visualization. As one example, the illustration of FIG. 12A may represent a topology mapping visualization where an accompanying header may include input fields to receive input corresponding to a source construct and a destination construct. It should be understood that the input fields may be located at other positions within a graphical user interface.

Following receipt of the user input corresponding to the selection of the source construct and the destination construct, the path determination logic 906 analyzes the construct metadata and the network data received from the controller and one or more constructs, respectively (block 1006). The analyses may result in a determination of a data transmission path between the source construct and the destination construct.

For example, in one embodiment, an analysis performed by the path determination logic 906 may include utilization of Dijkstra's algorithm (or Dijkstra's Shortest Path First algorithm, SPF algorithm) to determine the shortest path between the source construct and the destination construct based on the construct metadata and network data. In such an embodiment, the path determination logic 906 may determine that the data transmission is the shortest path per Dijkstra's algorithm, as discussed above.

Although Dijkstra's algorithm is well-known in the art, it is important to note that current systems are unable to obtain data in order determine the data transmission path according to Dijkstra's algorithm, or otherwise, especially when multiple hops are involved. Specifically, the copilot logic 138 as deployed in the distributed cloud management system 100 provides numerous technical advantages over conventional solutions. For example, with reference to FIG. 1, the copilot logic 138 receives construct metadata from the controller 102 and network data from each construct, which enables the copilot logic 138 to determine a topology of the network environment established by the controller and the constructs managed thereby, where the network environment may be a multi-cloud network environment.

One specific advantage over conventional solutions is that the copilot logic 138 obtains construct metadata and network data, which enables the copilot logic 138 to determine a complete topology of the network environment. In contrast, as discussed above, conventional solutions fails to obtain such data, and is not configured to enable a software instance to communicate with (1) a controller that provides construct metadata, potentially across multiple cloud networks, and (2) each construct managed by the controller to directly obtain network data corresponding to the construct.

A second specific advantage over conventional solutions is that the copilot logic 138 is configured to obtain construct metadata and network data corresponding to constructs and edges spanning multiple cloud networks. Cloud providers fall short of providing the technical advantages disclosed herein by merely generating a dashboard displaying statistics or metadata of constructs on its cloud network for clients (e.g., customers). For example, a client that utilizes multiple cloud providers is unable to obtain a visualization of the entire topology of their constructs from a single cloud provider's dashboard. Further, the client is certainly unable to obtain an understanding of network data across multiple clouds from conventional solutions. Stated otherwise, a dashboard provided a cloud provider presenting statistics or metadata of its cloud does not provide a client an understanding of connections between constructs deployed in multiple clouds or network metrics that present a data transmission path between constructs, latencies between each construct, CPU usage, memory usage or throughput rate.

Following the determination of the data transmission path, the interface generation logic 212 in combination with the path determination logic 906 generates a visualization illustrating the data transmission path between the source construct and the destination construct (block 1008). In some embodiments, the data transmission path may be illustrated directly on the topology mapping visualization. For example, with reference to FIG. 12B, one exemplary embodiment of a topology mapping visualization including a data transmission path illustrated thereon. It should be understood that the data transmission path may be illustrated in various manners and that the disclosure is not intended to be limited to a data transmission path being illustrated as double-arrow lines between constructs within the data transmission path. In embodiments in which the data transmission path is illustrated directly on a topology mapping visualization, the data transmission path may be illustrated in any emphasized or highlighted manner such that the data transmission path is visually distinct from other edges of the topology mapping visualizations.

Additionally, the method 1000 may include an optional operation of receiving, by the network metric determination logic 908, further user input corresponding to selection of an edge or construct included within the data transmission path (block 1010). Following receipt of selection of an edge or construct within the data transmission path, the interface generation logic 212 in combination with the network metric determination logic 908 may update the visualization to display network metrics associated with the selected edge or construct (block 1012).

Referring to FIG. 11, a flowchart of an exemplary method of comprising operations to determine a data transmission path within a cloud network and accompanying network metrics and generate a visualization of the data transmission path and network metrics is shown according to some embodiments. Each block illustrated in FIG. 11 represents an operation performed in the method 1100 of determining a data transmission path within a cloud network between a source construct and a destination construct and generating a visualization and report thereof. It is noted that the assumptions as discussed with respect to FIG. 10 apply equally to the method 1100.

The method 1100 begins when the interface generation logic 212 in combination with the topology snapshot logic 216 generates one or more visualizations, such as a topology mapping visualization, based on the received construct metadata and network data (block 1102). Further, the path determination logic 906 may receive user input corresponding to a selection of a source construct and a destination construct, and determine a data transmission path between the source construct and the destination construct (block 1104).

Following determination of a data transmission path (and, optionally illustrating such as discussed above with respect to FIG. 10), the network metric determination logic 908 may receive further user input corresponding to a request for a report of network metrics associated with the data transmission path (block 1106). For example, referring to FIG. 12A, the header portion 1202 includes several input fields, which as one example, may include text fields to receive indication of a source construct and a destination construct, and buttons corresponding to the initiation of the illustration of a data transmission path between the source and destination constructs (as shown in FIG. 12B) and/or the initiation of the generation of a report pertaining to network metrics associated with the data transmission path (as shown in FIGS. 12C-12D). Further, an input button labeled “Report” may be configured to receive user input (e.g., activation) and correspond to the initiation of the generation such a report.

In response to receipt of the request for a report of network metrics associated with the data transmission path, the network metric determination logic 908 determines the corresponding metrics (block 1108). For instance, the network metric determination logic 908 may perform operations that include that computation of latency periods between gateways included in the data transmission path, the computation of a total latency period for the data transmission path, computation of CPU usage and memory usage by each of the gateways included in the data transmission path, and computation of throughput at each gateway included in the data transmission path.

The interface generation logic 212 then generates a visualization illustrating the network metrics associated with the one or more edges or constructs included in the data transmission path (block 1110). For example, with reference to FIGS. 12C-12D, one exemplary embodiment of a report is illustrated as including an isolated data transmission path (in contrast to an overlay of FIG. 12B) and one or more tables and/or charts illustrating network metric data, which includes, but is not limited or restricted to, latencies between constructs, total latency, CPU usage, memory usage, and throughput (“Rx/Tx Rate”).

Referring now to FIGS. 12A-12C, exemplary interface screens displaying portions of additional aspects of a visualization platform directed to illustrating information describing the flow of network traffic through one or more constructs within a cloud-computing environment are shown according to some embodiments. Specifically, FIG. 12A illustrates an exemplary illustration of a dashboard 1200 similar to the dashboard 300 discussed above, at least with respect to FIG. 3A, where the dashboard 1200 includes a header portion 1202 and the navigation pane 1203 (similar to the navigation pane 304). The dashboard 1200 may also display the topology mapping 1204 generated by the copilot logic 138 in accordance with some embodiments.

As shown, the topology mapping 1204, which is similar to the topology mapping 400 of FIG. 4A, includes a graphical representation of the constructs managed by a controller, e.g., the controller 102 of FIG. 1. The topology mapping 1204 enables a user to visualize all known constructs, which may be deployed on a single cloud or across multiple cloud networks. It should be understood that the topology mapping 1204 represents a sample mapping and such mappings generated by the copilot logic 138 may include tens, hundreds, thousands, etc., of constructs and edges. The topology mapping 1204 is an interactive display screen configured to receive various forms of user input (e.g., drag and reposition of constructs, select construct(s) to view construct parameters, input text, select settings, or activate buttons, etc.). The received user input may be configured reposition constructs, cause a display of construct parameters, apply filters, search for constructs, run diagnostics, apply tag(s), etc.

As illustrated in FIG. 12A, the header portion 1202 includes several input fields, which as one example, may include text fields to receive indication of a source construct and a destination construct, where a data transmission path may be determined therebetween. As shown, sample input indicates “App-1” is the source node and “DB-2” is the destination node in the illustration, where node refers to a construct.

The header 1202 further includes buttons corresponding to the initiation of the illustration of a data transmission path between the source and destination constructs (as shown in FIG. 12B) (“Show Path”) and/or the initiation of the generation of a report pertaining to network metrics associated with the data transmission path (as shown in FIGS. 12C-12D) (“Report”). As discussed above, the input button labeled “Report” may be configured to receive user input (e.g., activation) and correspond to the initiation of the generation such a report. It should be understood that discussion of a particular type of user input field (e.g., text box, button, etc.) is not intended to be limiting. Instead, illustration of and reference to a particular type of a user input field is merely for the sake of clarity.

Referring to FIG. 12B, an exemplary illustration of a portion 1206 of the topology mapping 1204 generated by the copilot logic 138 and including a data transmission path 1208 between a source construct 1210 and a destination construct 1212 is shown in accordance with some embodiments. Following the discussion of FIG. 12A, the data transmission path 1208 may be generated in response to receipt of user input activating the “Show Path” button of the header portion 1202, discussed above.

Operations that result in the illustration of the data transmission path 1208 may include those performed by the path determination logic 906 and, optionally, the network metric determination logic 908 as discussed above. For instance, the path determination logic 906 may receive user input corresponding to a selection of a source construct and a destination construct, and analyze the construct metadata and the network data received associated with the source and destination constructs to determine a data transmission path between the source construct 1210 and the destination construct 1212.

It should be understood that the data transmission path 1208 may be illustrated in various manners and that the disclosure is not intended to be limited to the data transmission path 1208 being illustrated as double-arrow lines between constructs within the data transmission path 1208. In embodiments in which the data transmission path 1208 is illustrated directly on a topology mapping visualization as in FIG. 12B, the data transmission path 1208 may be illustrated in any emphasized or highlighted manner such that the data transmission path 1208 is visually distinct from other edges of the topology mapping 1206.

In some embodiments, the topology mapping 1206 may receive user input corresponding to selection of an edge of the data transmission path 1208. In response, the copilot logic 138 may be configured to display a latency 1214 associated with the selected edge as shown.

Referring to FIGS. 12C-12D, an exemplary illustration of a report corresponding to a data transmission path is illustrated in screens 1216 and 1226, wherein screen 1226 may be an extension of screen 1216 generated by the copilot logic 138. For example, in response to user input activating the “Report” button of the header portion 1202 with respect to a source construct “App-1” and a destination construct “DB-2,” the copilot logic 138 may generate a report including an isolated data transmission path between the source construct 1210 and the destination construct 1212 (in contrast to the overlay illustration of FIG. 12B). Further, the report may include a table 1218 having columns 1220, 1222 and 1224 that set forth a source gateway and a destination gateway of an edge within the data transmission path as well as a corresponding latency time for the edge. Thus, an IT administrator or other viewer may quickly assess whether any issues may be present with respect to latency time of a given edge. Quick assessment may enable quick resolution, or at least identification, or a problem within the data transmission path (e.g., Quality of Service (QoS) issues).

As noted above, the copilot logic 138 when deployed within the distributed cloud management system 100 provides numerous technical advantages over conventional solutions. One such technical advantage is illustrated in FIGS. 12B-12D, which includes an illustration of a data transmission path as well as metrics corresponding to the data transmission path in a single location. For instance, a viewer may gain an understanding of the data transmission path relative to a remaining portion a particular network (FIG. 12B) or see a visualization of an isolated data transmission path (FIG. 12C).

With reference to screen 1226 of FIG. 12D, further metrics associated with the data transmission path are shown in addition to the latency periods of the edges comprising the data transmission path. Some exemplary metrics that may be included in the report of FIGS. 12C-12D include CPU usage, memory usage and throughput (“Rx/Tx Rate”) of each gateway within the data transmission path. In one embodiment, the metrics may be aligned in a table format with rows 1228, 1230 and 1232 corresponding to gateways within the data transmission path and columns 1234, 1236 and 1238 referring to CPU usage, memory usage and Rx/Tx Rate, respectively.

In the foregoing description, the invention is described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. 

What is claimed is:
 1. A distributed cloud computing system comprising: a controller configured to deploy a plurality of gateways in a first cloud computing network; and logic, stored on non-transitory, computer-medium, that, upon execution by one or more processors, causes performance of operations including: generating a topology mapping of the first cloud computing network including a plurality of constructs and connections therebetween, wherein the plurality of constructs includes the plurality of gateways, receiving input corresponding to a selection of a source construct and a destination construct, determining a data transmission path between the source construct and the destination construct, generating a visualization illustrating the data transmission path, and causing rendering of the visualization on a display screen of a network device.
 2. The distributed cloud computing system of claim 1, wherein the determining of the data transmission path includes determination of a shortest path between the source construct and the destination construct.
 3. The distributed cloud computing system of claim 2, wherein determination of the shortest path includes application of Dijkstra's algorithm to the topology mapping.
 4. The distributed cloud computing system of claim 1, wherein the logic, that, upon execution by the one or more processors, causes performance of further operations includes: prior to generating the visualization, verifying the shortest path is an actual path within the first cloud computing network, wherein the verifying includes querying each gateway implicated in the shortest path to confirm that each gateway includes corresponding connections as set forth in the shortest path, wherein the plurality of gateways in the first cloud computing network include each gateway implicated in the shortest path.
 5. The distributed cloud computing system of claim 1, wherein generating the topology mapping includes: transmitting one or more requests to the controller for metadata of each of the plurality of gateways, receiving, from the plurality of gateways, network data associated with the plurality of gateways, and generating the topology mapping of the first cloud computing network.
 6. The distributed cloud computing system of claim 1, wherein the controller is configured to deploy a second plurality of gateways in a second cloud computing network, and wherein generating the topology mapping of the first cloud computing network includes generating the topology mapping to include constructs and connections of the both the first cloud computing network and the second cloud computing network, wherein the first cloud computing network is provided by a first cloud service provider and the second cloud computing is provided by a second cloud service provider.
 7. The distributed cloud computing system of claim 1, wherein the data transmission path spans both the first cloud computing network and the second cloud computing network.
 8. The distributed cloud computing system of claim 1, wherein the logic, that, upon execution by the one or more processors, causes performance of further operations includes: receiving further input corresponding to a request for a report of network metrics associated with the data transmission path, generating a report visualization illustrating the report of network metrics associated with the data transmission path, and causing rendering of the report visualization on the display screen of the network device.
 9. The distributed cloud computing system of claim 8, wherein the network metrics include one or more of latency periods between gateways included in the data transmission path, a total latency period for the data transmission path, CPU usage and memory usage by each gateway included in the data transmission path, or throughput at each gateway included in the data transmission path.
 10. The distributed cloud computing system of claim 8, wherein the report visualization includes one or more graphical representations of one or more of the network metrics associated with the data transmission path.
 11. The distributed cloud computing system of claim 1, wherein a construct of the plurality of constructs includes a software instance of one of a gateway, a virtual private cloud network (VPC), a virtual machine instance or a software application instance.
 12. A method for management of cloud computing networks, the method comprising: deploying a plurality of gateways in one or more cloud computing networks, wherein a controller deploys the plurality of gateways; generating a topology mapping of the one or more cloud computing networks including a plurality of constructs and connections therebetween, wherein the plurality of constructs includes the plurality of gateways; receiving input corresponding to a selection of a source construct and a destination construct; determining a data transmission path between the source construct and the destination construct; generating a visualization illustrating the data transmission path; and causing rendering of the visualization on a display screen of a network device.
 13. The method of claim 12, wherein determining the data transmission path includes determination of a shortest path between the source construct and the destination construct, wherein determination of the shortest path includes application of Dijkstra's algorithm to the topology mapping.
 14. The method of claim 12 further comprising: prior to generating the visualization, verifying the shortest path is an actual path within the first cloud computing network, wherein the verifying includes querying each gateway implicated in the shortest path to confirm that each gateway includes corresponding connections as set forth in the shortest path, wherein the plurality of gateways in the first cloud computing network include each gateway implicated in the shortest path.
 15. The method of claim 12, wherein generating the topology mapping includes: transmitting one or more requests to the controller for metadata of each of the plurality of gateways, receiving, from the plurality of gateways, network data associated with the plurality of gateways, and generating the topology mapping of the first cloud computing network.
 16. The method of claim 12, wherein the plurality of gateways are deployed across at least a first cloud computing network provided by a first cloud service provider and a second cloud computing provided by a second cloud service provider, and
 17. The method of claim 16, wherein the data transmission path spans both the first cloud computing network and the second cloud computing network.
 18. The method of claim 12 further comprising: receiving further input corresponding to a request for a report of network metrics associated with the data transmission path, generating a report visualization illustrating the report of network metrics associated with the data transmission path, wherein the report visualization includes one or more graphical representations of one or more of the network metrics associated with the data transmission path, and causing rendering of the report visualization on the display screen of the network device.
 19. The method of claim 18, wherein the network metrics include one or more of latency periods between gateways included in the data transmission path, a total latency period for the data transmission path, CPU usage and memory usage by each gateway included in the data transmission path, or throughput at each gateway included in the data transmission path.
 20. The method of claim 12, wherein a construct of the plurality of constructs includes a software instance of one of a gateway, a virtual private cloud network (VPC), a virtual machine instance or a software application instance. 